home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group98a.txt
/
000045_icon-group-sender _Tue Feb 24 08:19:37 1998.msg
< prev
next >
Wrap
Internet Message Format
|
2000-09-20
|
2KB
Return-Path: <icon-group-sender>
Received: from kingfisher.CS.Arizona.EDU (kingfisher.CS.Arizona.EDU [192.12.69.239])
by baskerville.CS.Arizona.EDU (8.8.7/8.8.7) with SMTP id IAA06769
for <icon-group-addresses@baskerville.CS.Arizona.EDU>; Tue, 24 Feb 1998 08:19:37 -0700 (MST)
Received: by kingfisher.CS.Arizona.EDU (5.65v4.0/1.1.8.2/08Nov94-0446PM)
id AA28252; Tue, 24 Feb 1998 08:19:36 -0700
Date: Wed, 11 Feb 1998 16:32:22 -0600
Message-Id: <199802112232.QAA20145@segfault.cs.utsa.edu>
From: Clinton Jeffery <jeffery@segfault.cs.utsa.edu>
To: icon-group@optima.CS.Arizona.EDU
Subject: Re: Stand-alone executables
Reply-To: jeffery@cs.utsa.edu
Errors-To: icon-group-errors@optima.CS.Arizona.EDU
Status: RO
Content-Length: 921
Wow, it seems almost EVERYBODY using DOS or Windows Icon wants stand-alone
executables. I sure do. The question is: who is going to volunteer? And
if no one volunteers, who is willing to pay for it?
Since it isn't research, I have continually been too short of "volunteer
time" to invest heavily in Microsoft-specific machine-level details, but
I am willing to work with anyone who volunteers to do this for the
command-line or graphical versions of Windows Icon. I am also willing to
hire and supervise a student to do the job, if we can come up with an
economic model to fund it.
Actually, some information might help at this point. Technical discussions
with the NT Spitbol implementor or with persons who know Microsoft's object
formats might reveal that the task isn't all that difficult. There are
several possible approaches, and I am not sure which would be easiest.
Clint Jeffery, jeffery@cs.utsa.edu